…asure the drift

The debt lived only in CLAUDE.md, docs/project-context.md and the sprint notes.
This project's own rule is that GitHub Issues are the single source of truth for
work items outside the BMad story flow, so a milestone task tracked in prose was
the one most likely to be forgotten — and it already had been: the milestone the
notes named (the close of Epic 4) passed on 2026-07-25 without it.

Both notes now point at #50, and both carry what was MEASURED rather than what
was assumed:

  · the drift is two commits, 59 insertions / 11 deletions — `7d4b1bd` (the D65
    post-completion section) and `da23f9f` (the source-tree diagram freshness
    pass). NEITHER touches a decision body, a dissent or a renunciation, which
    is what the views file gathers, so the content drift is smaller than the
    hash suggests;
  · there is NO generator. `cargo xtask` exposes only `ci`, whose views-hash
    check merely VERIFIES the frontmatter hash. "DERIVED — never edit by hand"
    has always meant "not independently of the source", not "a tool does it";
  · the bulk of the real work is re-checking that the 883-line view file's line
    citations still resolve, since architecture.md grew by 236 lines.

project-context.md's note also stops naming Epic 4's close as the milestone: a
sentence that describes a plan the project did not carry out reads as a fact and
sends the next reader to the wrong place.

No code changes. `cargo xtask ci` green.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>